Package | hl7.terminology |
Type | ValueSet |
Id | Id |
FHIR Version | R5 |
Source | http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-ActRelationshipSplit.html |
Url | http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplit |
Version | 3.0.0 |
Status | active |
Date | 2014-03-26 |
Name | ActRelationshipSplit |
Title | ActRelationshipSplit |
Experimental | False |
Realm | uv |
Authority | hl7 |
Description | A code specifying how branches in an action plan are selected among other branches. *Discussion:* This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches. In addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as "guard conditions" on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true. In exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true. |
Copyright | This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
No resources found
CodeSystem | |
v3-ActRelationshipSplit | ActRelationshipSplit |
Note: links and images are rebased to the (stated) source
Generated Narrative: ValueSet v3-ActRelationshipSplit
Language: en
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit
{
"resourceType" : "ValueSet",
"id" : "v3-ActRelationshipSplit",
"language" : "en",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet v3-ActRelationshipSplit</b></p><a name=\"v3-ActRelationshipSplit\"> </a><a name=\"hcv3-ActRelationshipSplit\"> </a><a name=\"v3-ActRelationshipSplit-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><ul><li>Include all codes defined in <a href=\"CodeSystem-v3-ActRelationshipSplit.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit</code></a></li></ul></div>"
},
"url" : "http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplit",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.1.11.10355"
}
],
"version" : "3.0.0",
"name" : "ActRelationshipSplit",
"title" : "ActRelationshipSplit",
"status" : "active",
"experimental" : false,
"date" : "2014-03-26",
"publisher" : "Health Level Seven International",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org"
},
{
"system" : "email",
"value" : "hq@HL7.org"
}
]
}
],
"description" : "A code specifying how branches in an action plan are selected among other branches.\r\n\r\n*Discussion:* This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches.\r\n\r\nIn addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as \"guard conditions\" on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true.\r\n\r\nIn exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true.",
"immutable" : true,
"copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
"compose" : {
"include" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit"
}
]
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.